Real-time digital assistant knowledge updates

ABSTRACT

Systems and processes are disclosed for real-time updating of virtual assistant media knowledge. Virtual assistant knowledge can be updated with timely information associated with playing media (e.g., a sporting event, a television show, or the like). A data feed can be received that includes data relating events to particular times in a media stream. A user request can be received based on speech input, and the user request can be associated with an event in a media stream or show. In response to receiving the request, the media stream can be cued to commence playback at a time in the media stream associated with the event referred to in the request. In another example, a response to the user request can be generated based on the data relating to the events. The response can then be delivered to the user (e.g., spoken aloud, displayed, etc.).

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority from U.S. Provisional Ser. No. 62/019,292, filed on Jun. 30, 2014, entitled REAL-TIME DIGITAL ASSISTANT KNOWLEDGE UPDATES, which is hereby incorporated by reference in its entirety for all purposes.

This application also relates to the following provisional application: U.S. Patent Application Ser. No. 62/019,312, “Intelligent Automated Assistant for TV User Interactions,” filed Jun. 30, 2014, which is hereby incorporated by reference in its entirety.

FIELD

This relates generally to voice control of television user interactions and, more specifically, to real-time updating of virtual assistant media knowledge.

BACKGROUND

Intelligent automated assistants (or virtual assistants) provide an intuitive interface between users and electronic devices. These assistants can allow users to interact with devices or systems using natural language in spoken and/or text forms. For example, a user can access the services of an electronic device by providing a spoken user input in natural language form to a virtual assistant associated with the electronic device. The virtual assistant can perform natural language processing on the spoken user input to infer the user's intent and operationalize the user's intent into tasks. The tasks can then be performed by executing one or more functions of the electronic device, and, in some examples, a relevant output can be returned to the user in natural language form.

While mobile telephones (e.g., smartphones), tablet computers, and the like have benefited from virtual assistant control, many other user devices lack such convenient control mechanisms. For example, user interactions with media control devices (e.g., televisions, television set-top boxes, cable boxes, gaming devices, streaming media devices, digital video recorders, etc.) can be complicated and difficult to learn. Moreover, with the growing sources of media available through such devices (e.g., over-the-air TV, subscription TV service, streaming video services, cable on-demand video services, web-based video services, etc.), it can be cumbersome or even overwhelming for some users to find desired media content to consume. In addition, coarse time-shifting and cue controls can make it difficult for users to obtain desired content, such as specific moments in a television program. Obtaining timely information associated with live media content can also be challenging. As a result, many media control devices can provide an inferior user experience that can be frustrating for many users.

SUMMARY

Systems and processes are disclosed for real-time updating of virtual assistant media knowledge. In one example, virtual assistant knowledge can be updated with timely information associated with playing media. A data feed can be received that includes data relating events to particular times in a media stream. A user request can be received based on speech input, and the user request can be associated with an event in a media stream or show. In response to receiving the request, the media stream can be cued to commence playback at a time in the media stream associated with the event referred to in the request.

In another example, timely information can be integrated into digital assistant knowledge to provide answers to queries involving current events. A data feed can be received that includes data relating events to particular times in a media stream. A user request can be received based on speech input from a user, and the user request can be associated with one of the events. A response to the user request can be generated based on the data relating to the event. The response can then be delivered to the user in a variety of ways (e.g., spoken aloud, displayed on a television, displayed on a mobile user device, etc.).

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary system for providing voice control of media playback and real-time updating of virtual assistant knowledge.

FIG. 2 illustrates a block diagram of an exemplary user device according to various examples.

FIG. 3 illustrates a block diagram of an exemplary media control device in a system for providing voice control of media playback.

FIG. 4 illustrates an exemplary process for voice control of media playback according to various examples.

FIG. 5 illustrates an exemplary data feed associating events in a media stream with particular times in the media stream.

FIG. 6 illustrates an exemplary virtual assistant query response of cuing video playback based on an event in a media stream.

FIG. 7 illustrates exemplary events appearing before and after a playback position that can be used to interpret user queries.

FIG. 8 illustrates an exemplary awards show data feed associating events in a media stream with particular times in the media stream.

FIG. 9 illustrates an exemplary television program data feed associating events in a media stream with particular times in the media stream.

FIG. 10 illustrates exemplary closed captioning text associated with a particular time in a video that can be used to respond to user queries.

FIG. 11A illustrates a television display with exemplary video content that can be used to interpret user queries.

FIG. 11B illustrates a mobile user device with exemplary image and text content that can be used to interpret user queries.

FIG. 12 illustrates an exemplary process for integrating information into digital assistant knowledge and responding to user requests.

FIG. 13 illustrates a functional block diagram of an electronic device configured to provide voice control of media playback and real-time updating of virtual assistant knowledge according to various examples.

FIG. 14 illustrates a functional block diagram of an electronic device configured to integrate information into digital assistant knowledge and respond to user requests according to various examples.

DETAILED DESCRIPTION

In the following description of examples, reference is made to the accompanying drawings in which it is shown by way of illustration specific examples that can be practiced. It is to be understood that other examples can be used and structural changes can be made without departing from the scope of the various examples.

This relates to systems and process for real-time updating of virtual assistant media knowledge. Real-time virtual assistant knowledge updates can, for example, enable precise voice control of television user interactions and provide timely and accurate virtual assistant responses to media related queries. In one example, a virtual assistant can be used to interact with a media control device, such as a television set-top box controlling content shown on a television display. A mobile user device or a remote control with a microphone can be used to receive speech input for the virtual assistant. The user's intent can be determined from the speech input, and the virtual assistant can execute tasks according to the user's intent, including causing playback of media on a connected television and controlling any other functions of a television set-top box or like device (e.g., causing playback of live media content, causing playback of recorded media content, managing video recordings, searching for media content, navigating menus, etc.).

In one example, virtual assistant knowledge can be updated with timely and even real-time information associated with playing media (e.g., a sporting event, a television show, or the like). A data feed can be received that includes data relating events to particular times in a media stream. For example, the data feed can indicate that a goal occurred at a certain time in a televised football game. In another example, the data feed can indicate that a show host delivered a monologue at a certain time in a televised show. A user request can be received based on speech input, and the user request can be associated with an event in a media stream or show. In response to receiving the request, the media stream can be cued to commence playback at a time in the media stream associated with the event referred to in the request.

In another example, timely or real-time information can be integrated into digital assistant knowledge to provide answers to queries involving current events. A data feed can be received that includes data relating events to particular times in a media stream. A user request can be received based on speech input from a user, and the user request can be associated with one of the events. A response to the user request can be generated based on the data relating to the event. The response can then be delivered to the user in a variety of ways (e.g., spoken aloud, displayed on a television, displayed on a mobile user device, etc.).

Updating virtual assistant knowledge with timely media information according to the various examples discussed herein can provide an efficient and enjoyable user experience. User interactions with media control devices can be intuitive and simple using a virtual assistant capable of receiving natural language queries or commands associated with media content. Real-time virtual assistant knowledge updates can, for example, enable precise voice control of television user interactions and provide timely and accurate virtual assistant responses to media related queries. In addition, desired portions or scenes of media can be made easily accessible using intuitive spoken commands relating to displayed media. It should be understood, however, that still many other advantages can be achieved according to the various examples discussed herein.

FIG. 1 illustrates exemplary system 100 for providing voice control of media playback and real-time updating of virtual assistant knowledge. It should be understood that voice control of media playback on a television as discussed herein is merely one example of controlling media on one type of display technology and is used for reference, and the concepts discussed herein can be used for controlling any media content interactions generally, including on any of a variety of devices and associated displays (e.g., monitors, laptop displays, desktop computer displays, mobile user device displays, projector displays, etc.). The term “television” can thus refer to any type of display associated with any of a variety of devices. Moreover, the terms “virtual assistant,” “digital assistant,” “intelligent automated assistant,” or “automatic digital assistant” can refer to any information processing system that can interpret natural language input in spoken and/or textual form to infer user intent, and perform actions based on the inferred user intent. For example, to act on an inferred user intent, the system can perform one or more of the following: identifying a task flow with steps and parameters designed to accomplish the inferred user intent; inputting specific requirements from the inferred user intent into the task flow; executing the task flow by invoking programs, methods, services, APIs, or the like; and generating output responses to the user in an audible (e.g., speech) and/or visual form.

A virtual assistant can be capable of accepting a user request at least partially in the form of a natural language command, request, statement, narrative, and/or inquiry. Typically, the user request seeks either an informational answer or performance of a task by the virtual assistant (e.g., causing display of particular media). A satisfactory response to the user request can include provision of the requested informational answer, performance of the requested task, or a combination of the two. For example, a user can ask the virtual assistant a question, such as “Where am I right now?” Based on the user's current location, the virtual assistant can answer, “You are in Central Park.” The user can also request the performance of a task, for example, “Please remind me to call Mom at 4 p.m. today.” In response, the virtual assistant can acknowledge the request and then create an appropriate reminder item in the user's electronic schedule. During the performance of a requested task, the virtual assistant can sometimes interact with the user in a continuous dialogue involving multiple exchanges of information over an extended period of time. There are numerous other ways of interacting with a virtual assistant to request information or performance of various tasks. In addition to providing verbal responses and taking programmed actions, the virtual assistant can also provide responses in other visual or audio forms (e.g., as text, alerts, music, videos, animations, etc.). Moreover, as discussed herein, an exemplary virtual assistant can control playback of media content (e.g., playing video on a television) and cause information to be displayed on a display.

An example of a virtual assistant is described in Applicants' U.S. Utility application Ser. No. 12/987,982 for “Intelligent Automated Assistant,” filed Jan. 10, 2011, the entire disclosure of which is incorporated herein by reference.

As shown in FIG. 1, in some examples, a virtual assistant can be implemented according to a client-server model. The virtual assistant can include a client-side portion executed on a user device 102 and a server-side portion executed on a server system 110. The client-side portion can also be executed on television set-top box 104 in conjunction with remote control 106. User device 102 can include any electronic device, such as a mobile phone (e.g., smartphone), tablet computer, portable media player, desktop computer, laptop computer, PDA, wearable electronic device (e.g., digital glasses, wristband, wristwatch, brooch, armband, etc.), or the like. Television set-top box 104 can include any media control device, such as a cable box, satellite box, video player, video streaming device, digital video recorder, gaming system, DVD player, Blu-ray Disc™ Player, a combination of such devices, or the like. Television set-top box 104 can be connected to display 112 and speakers 111 via a wired or wireless connection. Display 112 (with or without speakers 111) can be any type of display, such as a television display, monitor, projector, or the like. In some examples, television set-top box 104 can connect to an audio system (e.g., audio receiver), and speakers 111 can be separate from display 112. In other examples, display 112, speakers 111, and television set-top box 104 can be incorporated together in a single device, such as a smart television with advanced processing and network connectivity capabilities. In such examples, the functions of television set-top box 104 can be executed as an application on the combined device.

In some examples, television set-top box 104 can function as a media control center for multiple types and sources of media content. For example, television set-top box 104 can facilitate user access to live television (e.g., over-the-air, satellite, or cable television). As such, television set-top box 104 can include cable tuners, satellite tuners, or the like. In some examples, television set-top box 104 can also record television programs for later time-shifted viewing. In other examples, television set-top box 104 can provide access to one or more streaming media services, such as cable-delivered on-demand television shows, videos, and music as well as internet-delivered television shows, videos, and music (e.g., from various free, paid, and subscription-based streaming services). In still other examples, television set-top box 104 can facilitate playback or display of media content from any other source, such as displaying photos from a mobile user device, playing videos from a coupled storage device, playing music from a coupled music player, or the like. Television set-top box 104 can also include various other combinations of the media control features discussed herein, as desired.

User device 102 and television set-top box 104 can communicate with server system 110 through one or more networks 108, which can include the Internet, an intranet, or any other wired or wireless public or private network. In addition, user device 102 can communicate with television set-top box 104 through network 108 or directly through any other wired or wireless communication mechanisms (e.g., Bluetooth, Wi-Fi, radio frequency, infrared transmission, etc.). As illustrated, remote control 106 can communicate with television set-top box 104 using any type of communication, such as a wired connection or any type of wireless communication (e.g., Bluetooth, Wi-Fi, radio frequency, infrared transmission, etc.), including via network 108. In some examples, users can interact with television set-top box 104 through user device 102, remote control 106, or interface elements integrated within television set-top box 104 (e.g., buttons, a microphone, a camera, a joystick, etc.). For example, speech input including media-related queries or commands for the virtual assistant can be received at user device 102 and/or remote control 106, and the speech input can be used to cause media-related tasks to be executed on television set-top box 104. Likewise, tactile commands for controlling media on television set-top box 104 can be received at user device 102 and/or remote control 106 (as well as from other devices not shown). The various functions of television set-top box 104 can thus be controlled in a variety of ways, giving users multiple options for controlling media content from multiple devices.

The client-side portion of the exemplary virtual assistant executed on user device 102 and/or television set-top box 104 with remote control 106 can provide client-side functionalities, such as user-facing input and output processing and communications with server system 110. Server system 110 can provide server-side functionalities for any number of clients residing on a respective user device 102 or respective television set-top box 104.

Server system 110 can include one or more virtual assistant servers 114 that can include a client-facing I/O interface 122, one or more processing modules 118, data and model storage 120, and an I/O interface to external services 116. The client-facing I/O interface 122 can facilitate the client-facing input and output processing for virtual assistant server 114. The one or more processing modules 118 can utilize data and model storage 120 to determine the user's intent based on natural language input, and can perform task execution based on inferred user intent. In some examples, virtual assistant server 114 can communicate with external services 124, such as telephony services, calendar services, information services, messaging services, navigation services, television programming services, streaming media services, and the like, through network(s) 108 for task completion or information acquisition. The I/O interface to external services 116 can facilitate such communications.

Server system 110 can be implemented on one or more standalone data processing devices or a distributed network of computers. In some examples, server system 110 can employ various virtual devices and/or services of third-party service providers (e.g., third-party cloud service providers) to provide the underlying computing resources and/or infrastructure resources of server system 110.

Although the functionality of the virtual assistant is shown in FIG. 1 as including both a client-side portion and a server-side portion, in some examples, the functions of an assistant (or speech recognition and media control in general) can be implemented as a standalone application installed on a user device, television set-top box, smart television, or the like. In addition, the division of functionalities between the client and server portions of the virtual assistant can vary in different examples. For instance, in some examples, the client executed on user device 102 or television set-top box 104 can be a thin client that provides only user-facing input and output processing functions, and delegates all other functionalities of the virtual assistant to a backend server.

FIG. 2 illustrates a block diagram of exemplary user device 102 according to various examples. As shown, user device 102 can include a memory interface 202, one or more processors 204, and a peripherals interface 206. The various components in user device 102 can be coupled together by one or more communication buses or signal lines. User device 102 can further include various sensors, subsystems, and peripheral devices that are coupled to the peripherals interface 206. The sensors, subsystems, and peripheral devices can gather information and/or facilitate various functionalities of user device 102.

For example, user device 102 can include a motion sensor 210, a light sensor 212, and a proximity sensor 214 coupled to peripherals interface 206 to facilitate orientation, light, and proximity sensing functions. One or more other sensors 216, such as a positioning system (e.g., a GPS receiver), a temperature sensor, a biometric sensor, a gyroscope, a compass, an accelerometer, and the like, can also be connected to peripherals interface 206, to facilitate related functionalities.

In some examples, a camera subsystem 220 and an optical sensor 222 can be utilized to facilitate camera functions, such as taking photographs and recording video clips. Communication functions can be facilitated through one or more wired and/or wireless communication subsystems 224, which can include various communication ports, radio frequency receivers and transmitters, and/or optical (e.g., infrared) receivers and transmitters. An audio subsystem 226 can be coupled to speakers 228 and microphone 230 to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, and telephony functions.

In some examples, user device 102 can further include an I/O subsystem 240 coupled to peripherals interface 206. I/O subsystem 240 can include a touchscreen controller 242 and/or other input controller(s) 244. Touchscreen controller 242 can be coupled to a touchscreen 246. Touchscreen 246 and the touchscreen controller 242 can, for example, detect contact and movement or break thereof using any of a plurality of touch sensitivity technologies, such as capacitive, resistive, infrared, and surface acoustic wave technologies; proximity sensor arrays; and the like. Other input controller(s) 244 can be coupled to other input/control devices 248, such as one or more buttons, rocker switches, a thumb-wheel, an infrared port, a USB port, and/or a pointer device, such as a stylus.

In some examples, user device 102 can further include a memory interface 202 coupled to memory 250. Memory 250 can include any electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device; a portable computer diskette (magnetic); a random access memory (RAM) (magnetic); a read-only memory (ROM) (magnetic); an erasable programmable read-only memory (EPROM) (magnetic); a portable optical disc such as CD, CD-R, CD-RW, DVD, DVD-R, or DVD-RW; or flash memory such as compact flash cards, secured digital cards, USB memory devices, memory sticks, and the like. In some examples, a non-transitory computer-readable storage medium of memory 250 can be used to store instructions (e.g., for performing portions or all of the various processes described herein) for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device, and can execute the instructions. In other examples, the instructions (e.g., for performing portions or all of the various processes described herein) can be stored on a non-transitory computer-readable storage medium of server system 110, or can be divided between the non-transitory computer-readable storage medium of memory 250 and the non-transitory computer-readable storage medium of server system 110. In the context of this document, a “non-transitory computer-readable storage medium” can be any medium that can contain or store the program for use by or in connection with the instruction execution system, apparatus, or device.

In some examples, memory 250 can store an operating system 252, a communication module 254, a graphical user interface module 256, a sensor processing module 258, a phone module 260, and applications 262. Operating system 252 can include instructions for handling basic system services and for performing hardware-dependent tasks. Communication module 254 can facilitate communicating with one or more additional devices, one or more computers, and/or one or more servers. Graphical user interface module 256 can facilitate graphical user interface processing. Sensor processing module 258 can facilitate sensor-related processing and functions. Phone module 260 can facilitate phone-related processes and functions. Application module 262 can facilitate various functionalities of user applications, such as electronic messaging, web browsing, media processing, navigation, imaging, and/or other processes and functions.

As described herein, memory 250 can also store client-side virtual assistant instructions (e.g., in a virtual assistant client module 264) and various user data 266 (e.g., user-specific vocabulary data, preference data, and/or other data such as the user's electronic address book, to-do lists, shopping lists, television program favorites, etc.) to, for example, provide the client-side functionalities of the virtual assistant. User data 266 can also be used in performing speech recognition in support of the virtual assistant or for any other application.

In various examples, virtual assistant client module 264 can be capable of accepting voice input (e.g., speech input), text input, touch input, and/or gestural input through various user interfaces (e.g., I/O subsystem 240, audio subsystem 226, or the like) of user device 102. Virtual assistant client module 264 can also be capable of providing output in audio (e.g., speech output), visual, and/or tactile forms. For example, output can be provided as voice, sound, alerts, text messages, menus, graphics, videos, animations, vibrations, and/or combinations of two or more of the above. During operation, virtual assistant client module 264 can communicate with the virtual assistant server using communication subsystem 224.

In some examples, virtual assistant client module 264 can utilize the various sensors, subsystems, and peripheral devices to gather additional information from the surrounding environment of user device 102 to establish a context associated with a user, the current user interaction, and/or the current user input. Such context can also include information from other devices, such as from television set-top box 104. In some examples, virtual assistant client module 264 can provide the contextual information or a subset thereof with the user input to the virtual assistant server to help infer the user's intent. The virtual assistant can also use the contextual information to determine how to prepare and deliver outputs to the user. The contextual information can further be used by user device 102 or server system 110 to support accurate speech recognition.

In some examples, the contextual information that accompanies the user input can include sensor information, such as lighting, ambient noise, ambient temperature, images or videos of the surrounding environment, distance to another object, and the like. The contextual information can further include information associated with the physical state of user device 102 (e.g., device orientation, device location, device temperature, power level, speed, acceleration, motion patterns, cellular signal strength, etc.) or the software state of user device 102 (e.g., running processes, installed programs, past and present network activities, background services, error logs, resources usage, etc.). The contextual information can further include information associated with the state of connected devices or other devices associated with the user (e.g., media content displayed by television set-top box 104, media content available to television set-top box 104, etc.). Any of these types of contextual information can be provided to virtual assistant server 114 (or used on user device 102 itself) as contextual information associated with a user input.

In some examples, virtual assistant client module 264 can selectively provide information (e.g., user data 266) stored on user device 102 in response to requests from virtual assistant server 114 (or it can be used on user device 102 itself in executing speech recognition and/or virtual assistant functions). Virtual assistant client module 264 can also elicit additional input from the user via a natural language dialogue or other user interfaces upon request by virtual assistant server 114. Virtual assistant client module 264 can pass the additional input to virtual assistant server 114 to help virtual assistant server 114 in intent inference and/or fulfillment of the user's intent expressed in the user request.

In various examples, memory 250 can include additional instructions or fewer instructions. Furthermore, various functions of user device 102 can be implemented in hardware and/or in firmware, including in one or more signal processing and/or application specific integrated circuits.

FIG. 3 illustrates a block diagram of exemplary television set-top box 104 in system 300 for providing voice control of media playback. System 300 can include a subset of the elements of system 100. In some examples, system 300 can execute certain functions alone and can function together with other elements of system 100 to execute other functions. For example, the elements of system 300 can process certain media control functions without interacting with server system 110 (e.g., playback of locally stored media, recording functions, channel tuning, etc.), and system 300 can process other media control functions in conjunction with server system 110 and other elements of system 100 (e.g., playback of remotely stored media, downloading media content, processing certain virtual assistant queries, etc.). In other examples, the elements of system 300 can perform the functions of the larger system 100, including accessing external services 124 through a network. It should be understood that functions can be divided between local devices and remote server devices in a variety of other ways.

As shown in FIG. 3, in one example, television set-top box 104 can include memory interface 302, one or more processors 304, and a peripherals interface 306. The various components in television set-top box 104 can be coupled together by one or more communication buses or signal lines. Television set-top box 104 can further include various subsystems and peripheral devices that are coupled to the peripherals interface 306. The subsystems and peripheral devices can gather information and/or facilitate various functionalities of television set-top box 104.

For example, television set-top box 104 can include a communications subsystem 324. Communication functions can be facilitated through one or more wired and/or wireless communication subsystems 324, which can include various communication ports, radio frequency receivers and transmitters, and/or optical (e.g., infrared) receivers and transmitters.

In some examples, television set-top box 104 can further include an I/O subsystem 340 coupled to peripherals interface 306. I/O subsystem 340 can include an audio/video output controller 370. Audio/video output controller 370 can be coupled to a display 112 and speakers 111 or can otherwise provide audio and video output (e.g., via audio/video ports, wireless transmission, etc.). I/O subsystem 340 can further include remote controller 342. Remote controller 342 can be communicatively coupled to remote control 106 (e.g., via a wired connection, Bluetooth, Wi-Fi, etc.). Remote control 106 can include microphone 372 for capturing audio input (e.g., speech input from a user), button(s) 374 for capturing tactile input, and transceiver 376 for facilitating communication with television set-top box 104 via remote controller 342. Remote control 106 can also include other input mechanisms, such as a keyboard, joystick, touchpad, or the like. Remote control 106 can further include output mechanisms, such as lights, a display, a speaker, or the like. Input received at remote control 106 (e.g., user speech, button presses, etc.) can be communicated to television set-top box 104 via remote controller 342. I/O subsystem 340 can also include other input controller(s) 344. Other input controller(s) 344 can be coupled to other input/control devices 348, such as one or more buttons, rocker switches, a thumb-wheel, an infrared port, a USB port, and/or a pointer device, such as a stylus.

In some examples, television set-top box 104 can further include a memory interface 302 coupled to memory 350. Memory 350 can include any electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device; a portable computer diskette (magnetic); a random access memory (RAM) (magnetic); a read-only memory (ROM) (magnetic); an erasable programmable read-only memory (EPROM) (magnetic); a portable optical disc such as CD, CD-R, CD-RW, DVD, DVD-R, or DVD-RW; or flash memory such as compact flash cards, secured digital cards, USB memory devices, memory sticks, and the like. In some examples, a non-transitory computer-readable storage medium of memory 350 can be used to store instructions (e.g., for performing portions or all of the various processes described herein) for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device, and can execute the instructions. In other examples, the instructions (e.g., for performing portions or all of the various processes described herein) can be stored on a non-transitory computer-readable storage medium of server system 110, or can be divided between the non-transitory computer-readable storage medium of memory 350 and the non-transitory computer-readable storage medium of server system 110. In the context of this document, a “non-transitory computer-readable storage medium” can be any medium that can contain or store the program for use by or in connection with the instruction execution system, apparatus, or device.

In some examples, memory 350 can store an operating system 352, a communication module 354, a graphical user interface module 356, an on-device media module 358, an off-device media module 360, and applications 362. Operating system 352 can include instructions for handling basic system services and for performing hardware-dependent tasks. Communication module 354 can facilitate communicating with one or more additional devices, one or more computers, and/or one or more servers. Graphical user interface module 356 can facilitate graphical user interface processing. On-device media module 358 can facilitate storage and playback of media content stored locally on television set-top box 104 and other media content available locally (e.g., cable channel tuning). Off-device media module 360 can facilitate streaming playback or download of media content stored remotely (e.g., on a remote server, on user device 102, etc.). Application module 362 can facilitate various functionalities of user applications, such as electronic messaging, web browsing, media processing, gaming, and/or other processes and functions.

As described herein, memory 350 can also store client-side virtual assistant instructions (e.g., in a virtual assistant client module 364) and various user data 366 (e.g., user-specific vocabulary data, preference data, and/or other data such as the user's electronic address book, to-do lists, shopping lists, television program favorites, etc.) to, for example, provide the client-side functionalities of the virtual assistant. User data 366 can also be used in performing speech recognition in support of the virtual assistant or for any other application.

In various examples, virtual assistant client module 364 can be capable of accepting voice input (e.g., speech input), text input, touch input, and/or gestural input through various user interfaces (e.g., I/O subsystem 340 or the like) of television set-top box 104. Virtual assistant client module 364 can also be capable of providing output in audio (e.g., speech output), visual, and/or tactile forms. For example, output can be provided as voice, sound, alerts, text messages, menus, graphics, videos, animations, vibrations, and/or combinations of two or more of the above. During operation, virtual assistant client module 364 can communicate with the virtual assistant server using communication subsystem 324.

In some examples, virtual assistant client module 364 can utilize the various subsystems and peripheral devices to gather additional information from the surrounding environment of television set-top box 104 to establish a context associated with a user, the current user interaction, and/or the current user input. Such context can also include information from other devices, such as from user device 102. In some examples, virtual assistant client module 364 can provide the contextual information or a subset thereof with the user input to the virtual assistant server to help infer the user's intent. The virtual assistant can also use the contextual information to determine how to prepare and deliver outputs to the user. The contextual information can further be used by television set-top box 104 or server system 110 to support accurate speech recognition.

In some examples, the contextual information that accompanies the user input can include sensor information, such as lighting, ambient noise, ambient temperature, distance to another object, and the like. The contextual information can further include information associated with the physical state of television set-top box 104 (e.g., device location, device temperature, power level, etc.) or the software state of television set-top box 104 (e.g., running processes, installed applications, past and present network activities, background services, error logs, resources usage, etc.). The contextual information can further include information associated with the state of connected devices or other devices associated with the user (e.g., content displayed on user device 102, playable content on user device 102, etc.). Any of these types of contextual information can be provided to virtual assistant server 114 (or used on television set-top box 104 itself) as contextual information associated with a user input.

In some examples, virtual assistant client module 364 can selectively provide information (e.g., user data 366) stored on television set-top box 104 in response to requests from virtual assistant server 114 (or it can be used on television set-top box 104 itself in executing speech recognition and/or virtual assistant functions). Virtual assistant client module 364 can also elicit additional input from the user via a natural language dialogue or other user interfaces upon request by virtual assistant server 114. Virtual assistant client module 364 can pass the additional input to virtual assistant server 114 to help virtual assistant server 114 in intent inference and/or fulfillment of the user's intent expressed in the user request.

In various examples, memory 350 can include additional instructions or fewer instructions. Furthermore, various functions of television set-top box 104 can be implemented in hardware and/or in firmware, including in one or more signal processing and/or application specific integrated circuits.

It should be understood that system 100 and system 300 are not limited to the components and configuration shown in FIG. 1 and FIG. 3, and user device 102, television set-top box 104, and remote control 106 are likewise not limited to the components and configuration shown in FIG. 2 and FIG. 3. System 100, system 300, user device 102, television set-top box 104, and remote control 106 can all include fewer or other components in multiple configurations according to various examples.

Throughout this disclosure, references to “the system” can include system 100, system 300, or one or more elements of either system 100 or system 300. For example, a typical system referred to herein can include television set-top box 104 receiving user input from remote control 106 and/or user device 102.

In some examples, virtual assistant queries can include requests for particular media cued to a particular time. For example, a user might want to see a particular play in a game, a particular performance during a show, a particular scene in a movie, or the like. To handle such queries, the virtual assistant system can determine the user intent associated with a query, identify relevant media that is responsive to the query, and cue the media for playback at the appropriate time according to the user's request (e.g., cuing a game to begin playback just before someone scores a goal). Detailed media information can be incorporated in the virtual assistant's knowledge base to support a variety of media related queries. For instance, detailed media information can be incorporated into data and models 120 of virtual assistant server 114 of system 100 to support particular media queries. In some examples, detailed media information can also be obtained from external services 124 of system 100.

A responsive system capable of handling relevant user requests, however, can include incorporating real-time or near real-time media data into virtual assistant knowledge. For example, live sporting events can include a wide variety of points of interest that a user may wish to see. In addition, a video currently being watched by a user can include many points of interest that a user can refer to in queries. Similarly, a television program can include popular scenes, special guest appearances, widely discussed moments, or the like that a user may want cued for playback or identified to share with friends. Various other media content can likewise include relevant points of interest for users (e.g., music, web-based video clips, etc.). Detailed and timely media data, therefore, can be incorporated into virtual assistant knowledge according to various examples herein to support a variety of user requests associated with media, including even near real-time requests for content and media-related information.

FIG. 4 illustrates exemplary process 400 for voice control of media playback according to various examples, including incorporating detailed and/or timely media data. At block 402, a data feed can be received including events associated with times in a media stream. A data feed can be received in any of a variety of different forms and from a variety of difference sources. For example, a data feed can include a table correlating events and times in particular media, a database in which times are correlated with events, a text file associating events and times in particular media, an information server that provides times in response to event requests, or the like. Data feeds can come from a variety of different sources, such as external services 124 of system 100. In some examples, data feeds can be provided by organizations associated with particular media, such as sporting leagues that provide detailed sporting event information, video providers that provide detailed video and scene information, sports data aggregators that pull from multiple sports data sources, or the like. In other examples, data feeds can be obtained from analyzing media content, such as analyzing actor appearances, closed captioning text, scene changes, or the like. In still other examples, data feeds can be obtained from social media, such as popularly discussed moments of a show, frequently referenced events in a game, or the like. The term data feed as used herein can thus refer to a wide variety of data in a variety of forms, including data that can be mined from media itself.

FIG. 5 illustrates exemplary data feed 510 associating events in media stream 512 with particular times 514 in the media stream. It should be appreciated that FIG. 5 is provided for explanatory purposes, and data feed 510 can take a variety of other forms (e.g., text files, table files, informational server data, databases, messages, informational feeds, etc.). Media stream 512 can include any type of playable media, such as a sporting event, video, television program, music, or the like. In the example of FIG. 5, media stream 512 can include a televised ice hockey game. Overview information or other descriptive details of particular media can be included in data feed 510, whether associated with a particular time or not (e.g., can be included in a header or the like). In the illustrated example, descriptive overview information is provided in the first block at 5:01 (UTC), including a media title (e.g., “Ice Hockey Game”), a media description (“Team A vs. Team B at Ice Arena”), and a media source (e.g., televised on “Channel 7”). A variety of other descriptive information can similarly be provided, and information can be provided in particular fields for reference (e.g., a title field can include a title, a source field can include a television channel or Internet address, etc.). In addition to the information shown in FIG. 5, a variety of other media information can also be obtained, such as a roster of players on a team playing in a game, a list of actors appearing in an episode, producers, directors, artists, and the like. The various overview and descriptive information can all be incorporated into virtual assistant knowledge and used to support related queries.

As shown, data feed 510 can include media stream events 516 correlated with media stream times 514. Media stream times 514 can be designated in a variety of different ways, including using Coordinated Universal Time (abbreviated “UTC”), local time for the user, time at the virtual assistant server, time at the media server, time at the source of the media (e.g., a sports venue), or a variety of other time zones. In other examples, media stream times 514 can be provided as offsets from the beginning of media content (e.g., from the beginning of a movie, episode, sporting event, audio track, etc.). In still other examples, media stream times 514 can be provided as game clock times or the like. In any of the various examples, it should be appreciated that media stream times 514 can include precise time designations, such as seconds, milliseconds, or even finer gradations. For ease of reference, examples of media stream times 514 herein are provided with UTC hour and minute designations, although seconds can commonly be used, as can milliseconds or finer gradations.

Media stream events 516 can include a wide variety of events or points of interest in media stream 512. In sporting events, for example, media stream events 516 can include plays, penalties, goals, play segment divisions (e.g., periods, quarters, halves, etc.), play appearances (e.g., player at bat, players on ice, player in as quarterback, kicker on field, etc.), or the like. In a television program (e.g., a sitcom, talk show, etc.), media stream events 516 can include title sequences, character appearances, actor appearances (e.g., on-screen time designations), events within the program plot (e.g., particular scenes), guest appearances, guest performances, monologues, commercial breaks, or the like. In an awards show (e.g., movie award, theater awards, etc.), media stream events 516 can include monologues, award presentations, award recipient speeches, artist performances, commercial breaks, or the like. In a radio program, media stream events 516 can include opening remarks, guest speakers, discussion topics, or the like. It should therefore be appreciated that a wide variety of events or points of interest can be identified in any of a wide variety of media types, and those events can be associated with particular times in the media.

In other examples, points of interest or events can be identified based on social media, popular opinion, voting, or the like. For example, popular comments on a social media network associated with particular media (e.g., a live sporting event) can be used to identify likely points of interest and an approximate time of appearance (e.g., shortly before the first comments on the subject). In another example, viewers can indicate points of interest by marking times in media (e.g., using buttons on a remote, spoken requests, virtual buttons, or the like). In still other examples, points of interest can be identified from users sharing media with others, such as sharing a video clip from a certain portion of a media stream. Media stream events 516 in data feed 510 can thus be identified from media providers, users, social network discussions, and a variety of other sources.

In the example of FIG. 5, data feed 510 can include media stream events 516 associated with events in an ice hockey game. For example, puck drop beginning the first period of the game may have occurred at 5:07 (UTC), and data feed 510 can include an associated media stream event 516 at a particular media stream time 514 for that event. At 5:18 (UTC), a penalty may have been called against Player X for slashing Player Z, resulting in a two minute penalty. The details of the penalty (e.g., penalty type, players involved, penalty time, etc.) can be included in the media stream event 516 associated with the penalty at that particular media stream time 514. At 5:19 (UTC), a power play may have begun for Team A, and a media stream event 516 can be included that can be associated with the beginning of the power play with a particular media stream time 514. As shown, various other media stream events 516 can likewise be included and associated with particular media stream times 514. Details for different events can vary, and some or all of the information can be incorporated into virtual assistant knowledge. For example, details of a goal can include the player attributed with the goal and any assisting players. Details of the end of a power play can include identifying information for the team losing power play status and the team back at full force. Details of an on-screen player can include a coordinate location of the player on the screen. In addition, media stream events 516 can include time segment designations for a game, such as the end of the first period occurring at 5:31 (UTC).

In other examples, various other media stream events 516 with additional detailed information can be included in data feed 510 and/or determined from media stream 512 itself. For example, players on the ice can be associated with media stream times 514, changes in the score can be associated with media stream times 514, stoppages in play can be associated with media stream times 514, fights on the ice and fight participants can be associated with media stream times 514, and the like. In addition, various other details can be included in particular events or can be associated with a media stream, such as various statistics, player information, participant information (e.g., referees, coaches, etc.), game segment designators, and the like. In this manner, data feed 510 can include a detailed textual description of the various events 516 occurring in media stream 512 at various times 514.

It should be understood that media stream 512 need not be received to incorporate the knowledge of media stream events 516 and media stream times 514 into a virtual assistant's knowledge base. In some examples, without media stream 512, the information of data feed 510 can be received by virtual assistant server 114 to incorporate the information into virtual assistant knowledge (e.g., into data and models 120). Media stream 512, on the other hand, can be provided directly to user device 102, television set-top box 104, or another user device. As discussed below, in some examples, virtual assistant knowledge of media events 516 can be used to cue playback of media stream 512 on user devices (e.g., on user device 102, television set-top box 104, etc.), as well as to respond to other virtual assistant queries. In other examples, media stream 512, portions of media stream 512, and/or metadata associated with media stream 512 can be received by virtual assistant server 114 and incorporated in the virtual assistant's knowledge base.

Referring again to process 400 of FIG. 4, at block 404, a spoken user request can be received that is associated with an event in a media stream. As discussed above, speech input can be received from a user in a variety of ways, such as via user device 102, remote control 106, or another user device in system 100. Speech input directed to the virtual assistant can include a variety of user requests, including requests associated with media and/or events within particular media. For example, a user request can include references to any of the media stream events 516 discussed herein, such as a query associated with an ice hockey game event shown in FIG. 5. In some examples, user requests can include requests to cue media to a particular point of interest. For example, users might request to see a fight in an ice hockey game (e.g., “show me the fight between Player Y and Player Q”), jump to the beginning of a period (e.g., “jump to the first period puck drop.”), watch a goal (e.g., “show me Player M's goal”), see what resulted in a particular penalty (e.g., “show me the slashing penalty against Player X”), or the like.

Referring again to process 400 of FIG. 4, at block 406, playback of a media stream can be caused to commence at a time in the media stream associated with an event in a user request. For example, knowledge incorporated in the virtual assistant knowledge base from data feed 510 can be used to determine a particular time in a media stream associated with a user's request for particular content. FIG. 6 illustrates an exemplary virtual assistant query response of cuing video playback based on an event in a media stream that is responsive to the query. In the illustrated example, a user may be viewing display 112 with content controlled by television set-top box 104. The user may be viewing video 620, which can include an ice hockey game associated with data feed 510 discussed above. As discussed with reference to block 404 of process 400, the user may then request to view particular media content associated with an event. For example, the user might request to see a goal (e.g., “show me that goal again,” “show me Player M's goal,” “show me Team A's goal,” “show me the goal in the first period,” “show me the first goal in the A/B hockey game,” “replay that last goal,” etc.).

In response to the user's request, a particular time in the media stream (e.g., in video 620) that is responsive to the user's request can be determined. In this example, using knowledge incorporated in the virtual assistant's knowledge base from data feed 510 of FIG. 5, the system can identify the Team A goal of Player M assisted by Player Q at 5:21 (UTC) as shown in FIG. 5. The system can then cause video 620 to time-shift to the appropriate time to show the desired content. In this example, the system can time-shift video 620 to commence playback at cued time 624 indicated on playback indicator 622. As shown, cued time 624 can differ from live time 626 (e.g., the time associated with the live televised or otherwise live distributed stream of content). In some examples, cued time 624 can correspond to the media stream time 514 associated with the corresponding media stream event 516. In other examples, cued time 624 can be shifted earlier or later than media stream time 514 depending on how media stream events 516 are associated with media stream times 514. For example, cued time 624 can be thirty seconds, a minute, two minutes, or another amount before the corresponding media stream time 514 to capture play just prior to a goal being scored. In some examples, data feed 510 can include precise time designations of where playback should begin for particular events (e.g., designating when a hockey player began to make a drive for the eventual goal, designating when penalty behavior was first seen, etc.). Video 620 can thus be played for the user beginning at cued time 624 in response to the user's virtual assistant request.

In some examples, video 620 can replace another video shown on display 112, or can otherwise be retrieved for playback in response to a user's request. For example, a user viewing other content can utter a request to see the last goal scored in a hockey game on another channel (e.g., “show me the last goal scored in the hockey game on channel seven,” “show me the last goal of the A/B hockey game,” “show me the first goal in the Ice Arena game,” etc.). As discussed above, if a user's request cannot be resolved to particular media, the virtual assistant can prompt for more information or a confirmation as needed (e.g., “Did you mean the Team A vs. Team B ice hockey game at Ice Arena showing on Channel 7?”) With the request resolved to particular content, television set-top box 104 can retrieve video 620 for playback and cue it to cued time 624. It should be appreciated that video 620 can be played on user device 102 or any other device, and the virtual assistant can similarly cue video 620 to cued time 624 on user device 102 or another device (e.g., based on a specific user command, based on the device on which the user is watching video 620, based on the source of the user request, etc.).

In some examples, user requests directed to a virtual assistant can include ambiguous references to something shown on display 112 by television set-top box 104 or shown on touchscreen 246 of user device 102. For example, a request related to video 620 shown on display 112 in FIG. 6 can include an ambiguous reference to on-screen player 628 or on-screen player 630. The particular player the user is asking about or referencing can be unclear from the speech input alone. In another example, user requests can include other references that would otherwise be ambiguous from speech input alone. For example, a request to see team rosters can be ambiguous without knowing that the user is watching a particular game with particular teams, a request to see the next goal can be ambiguous without knowing that the user is watching a particular game, etc. The content shown on display 112 and associated metadata (e.g., from data feed 510 or otherwise) can thus be used to disambiguate user requests and determine user intent. For example, on-screen actors, on-screen players, a list of game participants, a list of actors in a show, a team roster, or the like can be used to interpret user requests.

In the illustrated example, the content shown on display 112 and associated metadata can be used to determine the user intent from a reference to “the goalie,” “that player,” “number eight,” “him,” “M,” a nickname, or any other reference related to the particular game and/or the particular on-screen players. For example, as noted above, data feed 510 can include an indication of which players appear on screen at particular times, which players are involved in a particular event, which players are on the ice at a particular time, and the like. At the time associated with FIG. 6, for example, the knowledge incorporated into the virtual assistant knowledge base from data feed 510 can indicate that Player M (e.g., on-screen player 628) and the goalie (e.g., on-screen player 630) are on screen at that particular time, on the ice around that time, playing in that game, or at least are likely to be on screen or of relevance at that particular time. Requests referencing “the goalie,” “that player,” “number eight,” “him,” “M,” a nickname, or the like can then be disambiguated based on that information.

For example, a request to see “the goalie's” last stop (e.g., “show me the goalie's last stop”) can be resolved to the particular goalie corresponding to on-screen player 630 (as opposed to an alternate or a goalie from the other team), and his name or other identifying information can be used to identify content responsive to the user's query (e.g., the most recent stop by that particular goalie in the current game, the last stop by that particular goalie in a prior game, etc.). In another example, a request to see “eight's” next goal (e.g., “show me eight's next goal”) can be resolved to a particular player with the number eight or the nickname eight (e.g., on-screen player 628) based on data feed 510 and associated metadata. Content responsive to the query can then be identified based on identifying information of the player corresponding to “eight” (e.g., Player M's next goal in this game, Player M's next goal in a subsequent game, etc.). In other examples, content shown on display 112 or on user device 102 can be analyzed to interpret user requests in other ways. For example, facial recognition, image recognition (recognizing jersey numbers), or the like can be used to identify on-screen players 628 and 630 to interpret associated user requests. It should be understood that responses to user requests can include informational responses and/or media content responses, and responses can be displayed on any device (e.g., display 112, touchscreen 246, etc.).

Although various examples have been provided herein, it should be appreciated that users can refer to players (as well as actors, characters, etc.) in a variety of different ways, all of which can be disambiguated according to the examples discussed herein. For example, users can refer to a player by name (e.g., first name, last name, full name, nickname, etc.), number, position, team, depth chart (e.g., “2nd string QB”), game-specific identifiers (e.g., starter, substitute, reliever, closer, etc.), years experience (e.g., rookie, freshman, sophomore, etc.), team designations (e.g., captain, alternate captain, etc.), gameplay style (e.g., enforcer, speedy, etc.), former teams, college (e.g., “the QB from Q University”), statistical information (e.g., “the fight by the player that scored a hat trick,” “the penalty by the team's top scorer,” etc.), biographical information (e.g., “the son of Hall-of-Famer O,” “the next at bat by that pitcher from West Virginia,” etc.), physical appearance (e.g., tall, short, skin color, clothing, etc.), sponsors (e.g., “the crash by the Hardware Store car”), and the like.

In other examples, user requests directed to a virtual assistant can include ambiguous references based on a current playback position of something shown on display 112 by television set-top box 104 or shown on touchscreen 246 of user device 102. For example, users might refer to the “next” goal, the “previous” penalty, the “next” commercial, the “last” performance, the “next” actor appearance, or the like. The user intent (e.g., the specific desired content) can be unclear from the speech input alone. In some examples, however, a current playback position in a media stream can be used to disambiguate user requests and determine user intent. For instance, a media stream time indicating the current playback position can be sent to and used by the virtual assistant system to interpret user requests.

FIG. 7 illustrates media stream 512 with exemplary media stream events 516 appearing before and after current playback position 732, which can be used to interpret user queries (e.g., to disambiguate user requests and determine user intent). As shown, live time 626 can be later than the current playback position 732, and, in some examples, media stream 512 can include a recording of content that is no longer live. Given current playback position 732 as shown, various references to media stream events 516 can be interpreted, such as “next” and “previous” events. For example, a user request to see the previous or last goal (e.g., “show me the last goal”) can be ambiguous based on the speech input alone, but current playback position 732 can be used to interpret the user request (e.g., resolving the reference “last”) and identify previous goal 734 as the desired media stream event 516. In another example, a user request to see the next penalty (e.g., “show me the next penalty”) can be ambiguous based on the speech input alone, but current playback position 732 can be used to interpret the user request (e.g., resolving the reference “next”) and identify next penalty 738 as the desired media stream event 516. Current playback position 732 can be used to interpret requests for previous penalty 736 and next goal 740 in a similar manner, as well as used to interpret various other positional references (e.g., the next two, the last three, etc.).

FIG. 8 illustrates exemplary data feed 810 associating events in media stream 812 with particular times 514 in the media stream. Data feed 810 can include similar features as data feed 510 discussed above, and data feed 810 can similarly be received at block 402 and used to cause playback of media at block 406 of process 400 discussed above. In the example of FIG. 8, media stream 812 can include a televised awards show. In other examples, a similar media stream could include an Internet-based awards show, a radio program show, a variety show, or the like. Overview information or other descriptive details of particular media can be included in data feed 810, whether associated with a particular time or not (e.g., can be included in a header or the like). In the illustrated example, descriptive overview information is provided in the first block at 10:59 (UTC), including a media title (e.g., “Movie Awards”), a media description (“annual movie awards hosted by comedian Whitney Davidson”), and a media source (e.g., televised on “Channel 31”). A variety of other descriptive information can similarly be provided, and information can be provided in particular fields for reference (e.g., a title field can include a title, a source field can include a television channel or Internet address, etc.). In addition to the information shown in FIG. 8, a variety of other media information can also be obtained, such as participant names, performance descriptions, awards given, etc. The various overview and descriptive information can all be incorporated into virtual assistant knowledge and used to support related queries.

As shown, data feed 810 can include media stream events 516 correlated with media stream times 514, which can be similar to events 516 and times 514 discussed above with reference to FIG. 5. Media stream events 516 in data feed 810 can include a wide variety of events or points of interest in media stream 812. In an awards show (e.g., movie awards, theater awards, etc.) like media stream 812, for example, media stream events 516 can include monologues, award presentations, award recipient speeches, participant appearances, performance descriptions, commercial breaks, or the like.

In other examples, points of interest or events can be identified based on social media, popular opinion, voting, or the like. For example, popular comments on a social media network associated with particular media (e.g., a live awards show) can be used to identify likely points of interest and an approximate time of appearance (e.g., shortly before the first comments on the subject). In another example, viewers can indicate points of interest by marking times in media (e.g., using buttons on a remote, spoken requests, virtual buttons, or the like). In still other examples, points of interest can be identified from users sharing media with others, such as sharing a video clip from a certain portion of a media stream. Media stream events 516 in data feed 810 can thus be identified from media providers, users, social network discussions, and a variety of other sources.

In the example of FIG. 8, data feed 810 can include media stream events 516 associated with events in an awards show. For example, an opening monologue by a comedian named Whitney Davidson may have occurred at 11:00 (UTC), and data feed 810 can include an associated media stream event 516 at a particular media stream time 514 for that event. At 11:08 (UTC), a design award for best costume may have been presented by actors named Jane Doe and John Richards to a recipient designer named Jennifer Lane. The details of the award presentation (e.g., award name, presenters, recipient, etc.) can be included in the media stream event 516 associated with the award presentation at that particular media stream time 514. At 11:10 (UTC), the best costume design award recipient may have given a speech, and a media stream event 516 can be included at that time with associated details (e.g., award type, recipient, speaker, etc.). At 11:12 (UTC), a musical performance titled “Unforgettable” may have been performed by a singer named David Holmes, and a media stream event 516 can be included with associated details at the corresponding time 514. As shown, various other media stream events 516 can likewise be included and associated with particular media stream times 514. Details for different events can vary, and some or all of the information can be incorporated into virtual assistant knowledge.

In other examples, various other media stream events 516 with additional detailed information can be included in data feed 810 and/or determined from media stream 812 itself. For example, actors or participants appearing on screen can be associated with media stream times 514. Such information can be derived from provided data or can be derived by analyzing media stream 812 (e.g., using facial recognition or the like). In addition, various other details can be included in particular events or can be associated with a media stream, such as various statistics, participant information (e.g., audience members, producers, directors, etc.), and the like. In this manner, data feed 810 can include a detailed textual description of the various events 516 occurring in media stream 812 at various times 514. As discussed above, this information can be incorporated into the virtual assistant's knowledge base and used in responding to user requests, such as cuing video according to user requests as discussed above with reference to block 406 of process 400.

FIG. 9 illustrates exemplary data feed 910 associating events in media stream 912 with particular times 514 in the media stream. Data feed 910 can include similar features as data feed 510 and data feed 810 discussed above, and data feed 910 can similarly be received at block 402 and used to cause playback of media at block 406 of process 400 discussed above. In the example of FIG. 9, media stream 912 can include a television program, such as a sitcom. In other examples, a similar media stream could include a game show, news show, talk show, variety show, quiz show, virtual reality show, drama, soap opera, or the like. Overview information or other descriptive details of particular media can be included in data feed 910, whether associated with a particular time or not (e.g., can be included in a header or the like). In the illustrated example, descriptive overview information is provided in the first block at 14:00 (UTC), including a media title (e.g., “Television Program”), a media description (situational comedy with actors Jane Holmes (Character A) and David Doe (Character B)), and a media source (e.g., streamed from a web source). A variety of other descriptive information can similarly be provided, and information can be provided in particular fields for reference (e.g., a title field can include a title, a source field can include a television channel or Internet address, etc.). In addition to the information shown in FIG. 9, a variety of other media information can also be obtained, such as producers, directors, hosts, participant names, participant characteristics, actors, plot descriptions, guests, etc. The various overview and descriptive information can all be incorporated into virtual assistant knowledge and used to support related queries.

As shown, data feed 910 can include media stream events 516 correlated with media stream times 514, which can be similar to events 516 and times 514 discussed above with reference to FIG. 5. Media stream events 516 in data feed 910 can include a wide variety of events or points of interest in media stream 912. In a television program (e.g., TV episode, news show, talk show, etc.) like media stream 912, for example, media stream events 516 can include performance descriptions (e.g., scene descriptions, performer appearances, etc.), show segment designators (e.g., monologue, sendoff, title sequence, guest appearance, bonus round, etc.), commercial breaks, or the like.

In other examples, points of interest or events can be identified based on social media, popular opinion, voting, or the like. For example, popular comments on a social media network associated with particular media (e.g., a new episode of a popular sitcom, a nightly talk show, etc.) can be used to identify likely points of interest and an approximate time of appearance (e.g., shortly before the first comments on the subject). In another example, viewers can indicate points of interest by marking times in media (e.g., using buttons on a remote, spoken requests, virtual buttons, or the like). In still other examples, points of interest can be identified from users sharing media with others, such as sharing a video clip from a certain portion of a media stream. Media stream events 516 in data feed 910 can thus be identified from media providers, users, social network discussions, and a variety of other sources.

In the example of FIG. 9, data feed 810 can include media stream events 516 associated with events in a sitcom TV show. For example, a title sequence may have occurred at 14:01 (UTC), and data feed 910 can include an associated media stream event 516 at a particular media stream time 514 for that event. At 14:03 (UTC), in the plot of the show, two characters may have had a fight over a parking spot. The details of the scene or moment in the plot (e.g., characters on screen, actors on screen, description of what takes place, etc.) can be included in the media stream event 516 associated with the award presentation at that particular media stream time 514. At 14:06 (UTC), a guest start may have appeared in the show and performed a song, and a media stream event 516 can be included with associated details at the corresponding time 514. As shown, various other media stream events 516 can likewise be included and associated with particular media stream times 514. Details for different events can vary, and some or all of the information can be incorporated into virtual assistant knowledge.

In other examples, various other media stream events 516 with additional detailed information can be included in data feed 910 and/or determined from media stream 912 itself. For example, actors or participants appearing on screen can be associated with media stream times 514. Such information can be derived from provided data or can be derived by analyzing media stream 912 (e.g., using facial recognition or the like). In addition, various other details can be included in particular events or can be associated with a media stream, such as various statistics, participant information (e.g., audience members, producers, directors, etc.), and the like. In this manner, data feed 910 can include a detailed textual description of the various events 516 occurring in media stream 912 at various times 514. As discussed above, this information can be incorporated into the virtual assistant's knowledge base and used in responding to user requests, such as cuing video according to user requests as discussed above with reference to block 406 of process 400.

In any of the various examples discussed herein, additional virtual assistant knowledge can be derived from closed captioning text associated with particular media content. For example, the information for any of the data feeds discussed herein can be supplemented by or derived from closed captioning text. Additional media stream events 516 can be added at media stream times 514 based on closed captioning text associated with a particular time in media playback (e.g., identifying when a particular phrase was spoken, identifying when particular characters speak, etc.). In addition, closed captioning text can be used to disambiguate user requests and determine user intent according to various examples discussed herein (e.g., based on spoken names).

FIG. 10 illustrates exemplary closed captioning text 1054 associated with a particular time in video 1050, which can be used to respond to virtual assistant queries. In the illustrated example, closed captioning interface 1052 can include closed captioning text 1054 at current playback position 1056 of video 1050 shown on display 112. At current playback position 1056, characters 1060, 1062, and 1064 can appear on screen, and some of them can be speaking the text shown as closed captioning text 1054. In deriving information for virtual assistant knowledge, closed captioning text 1054 can be correlated with current playback position 1056. In some examples, time offset 1058 can be used as a reference (e.g., the text of closed captioning text 1054 can appear two minutes into video 1050, or similarly the equivalent speech can be spoken two minutes into video 1050).

A variety of information can be derived from closed captioning text 1054, and some of it can be associated with time offset 1058 as a particular media stream event 516. For example, spoken names can be used to infer character appearances on screen at particular times. The spoken word “Blanche” can, for example, be used to infer that a character named “Blanche” may appear on screen at or near time offset 1058 in video 1050. The derived information can then be used to respond to user requests associated with the character name “Blanche” or a corresponding actress identified from metadata (e.g., “show me where Blanche comes in”). In another example, spoken phrases can be identified and associated with a particular time they were spoken. The spoken phrase “formidable family” can, for example, be identified as being spoken at or near time offset 1058 in video 1050. The derived information can then be used to respond to user requests associated with the spoken phrase “formidable family” (e.g., “show me where Blanche says formidable family”). Closed captioning text can thus be analyzed and associated with particular times, and the combination can be incorporated into virtual assistant knowledge to respond to related user requests.

It should be understood that information can be derived from closed captioning text 1054 whether or not it is shown in an interface, such as interface 1052. For example, closed captioning text can be analyzed without actually playing a corresponding video, and times can be derived from metadata associated with the closed captioning. Moreover, although shown on display 112 in FIG. 10, it should be understood that closed captioning can be analyzed to derive virtual assistant knowledge at a server or another device, with or without actually playing the associated video.

As discussed above, speech input received from a user can be ambiguous. In addition to the information noted above that can be used to interpret user requests (e.g., on-screen players, on-screen actors, playback position, etc.), a variety of other contextual information can be used to interpret user requests. For example, personal information about a user can be used to interpret user requests. A user can be identified based on voice recognition, logging into a device, entering a password, using a particular account, selecting a profile (e.g., age and gender), or the like. User-specific data for an identified user (or a particular household) can then be used to interpret user requests. Such user-specific data can include a user's favorite team, a user's favorite sport, a user's favorite player, a user's favorite actor, a user's favorite television show, a user's geographical location, a user demographic, a user's viewing history, a user's subscription data, or the like. In addition, user-specific data (or household-specific data) can include a viewing history of media content reflecting commonly watched shows, commonly watched sports, preferred genres, etc. Moreover, in some examples, generic age and gender data can be inferred from user speech (e.g., based on pitch, words used, etc.), which can then be used to bias results according to that profile (e.g., biasing words, shows, names, query results, and the like based on the likely preferences of the age and gender profile).

In some examples, user requests can specifically reference user-specific data. For example, users can refer to “my team” (e.g., “How's my team doing?”). User-specific data can then be used to resolve the reference “my team” to a particular sports team designated as the user's favorite team. In other examples, user-specific data can be used to bias speech recognition and user intent determination (e.g., inferring a particular user likely asked about a particular actor based on recently watched movies in which that actor appears). For example, actor or player names that a user likes, watches, or is otherwise associated with can be identified in user-specific data and used during speech recognition and intent determination to bias results in favor of those actor or player names. This can be helpful in accurately recognizing unique names, names that sound like other words or names, or the like.

In addition to the various other contextual sources discussed herein for accurately recognizing speech input and interpreting user requests, information from multiple devices associated with a user can be used as context for accurate speech recognition and for determining user intent. For example, a user watching television (e.g., on display 112) might also be consuming content on another device (e.g., on user device 102). Content from both devices can then be used in interpreting user requests.

FIG. 11A illustrates television display 112 showing video 1150. FIG. 11B illustrates user device 102 with touchscreen 246 showing displayed image 1170 and displayed text 1172. A user request can be received (e.g., via remote control 106 or user device 102) that references content from either device. For example, a user might request to show “Jennifer's” last goal. The reference to “Jennifer” can be unclear from the speech input alone. Displayed text 1172, however, can be used to disambiguate the request and identify Jennifer as the player appearing in the content shown on user device 102. Video content responsive to the request can then be identified based on the specific player, and the content can be played for the user. Responsive content can be provided on either display 112 or on user device 102 (e.g., based on a specific command, user preference, or the like).

In another example, names associated with video 1150 of FIG. 11A and names associated with displayed image 1170 and displayed text 1172 of FIG. 11B can be used during speech recognition to bias results toward likely name candidates or identify names that may be difficult to recognize. For example, a user request can include a name that may be ambiguous, but the names associated with content displayed on either device can be used to accurately identify the user's intent. In other examples, lists of actors, presenters, performers, producers, directors, participants, penalties, sports terms, and the like associated with content displayed on either device can similarly be used to improve speech recognition accuracy and determine user intent.

In some examples, displayed image 1170 of FIG. 11B can include a moving image or video. For example, the content shown in FIG. 11B can include secondary screen experience data (e.g., data and video intended to accompany another program), secondary camera view data (e.g., video with an alternative view or vantage point than what is primarily displayed for a particular program), or the like. Such information can be used to improve speech recognition accuracy and determine user intent in a similar manner as discussed above. In addition, whether shown on a separate user device or not, secondary screen experience data, secondary camera view data, and the like can be received and used as part of a data feed to identify relevant points of interest and associated times in a media stream. For example, a secondary screen experience can include descriptions of highlights in a game. Those descriptions can be included in virtual assistant knowledge as relevant media stream events with associated media stream times, and can be used to respond to user requests. Similarly, secondary camera view data can be included in virtual assistant knowledge as relevant media stream events identifying particular media stream times where alternative camera content may be available (which can, for example, be used in responding to certain user requests).

As noted above, in response to certain user requests, media can be played back beginning at particular cued times. In some examples, multiple segments of one or more media streams can be played back consecutively in response to some user requests. For example, users can request to view game highlights, all the goals of a game, all the fights in a game, all the appearances of a particular actor in a show, all the scenes for a particular character in a show, an opening monologue from each of multiple talk shows, a bonus round from each of multiple game shows, the best moments of a show or a variety of other media segments from one or more shows. In the same manner discussed above, particular times associated with the desired events can be identified in one or more shows, and playback can be caused to commence with a first segment followed consecutively by the other identified segments. In some examples, highlights, best moments, or the like can be determined based on bookmark popularity, social media discussions, replay counts, and the like. The end of each segment can be identified in a variety of ways, such as by a commercial break, another media event in the associated media stream, a default play time, a specific endpoint entry in media event details, or the like. In this manner, users can request, for example, highlight reels for specific content they want to see, and the system can automatically identify the desired highlights and play them back consecutively (or provide them for selectable playback in any other order or the like).

In some examples, users may want to share a particular segment of a media stream with friends, family, or the like. In one example, users can indicate a bookmark position in a media stream corresponding to a particular playback position in the media stream. This customized bookmark position can then be transmitted to a server and shared with friends via social networks, messaging, other television set-top boxes 104, other user devices 102, and the like. Users can indicate bookmarks using physical buttons, virtual buttons, speech input, or any other entry using remote control 106 and/or user device 102. For example, a user can direct a request to the virtual assistant system to bookmark a certain media segment and send it to a contact in the user's address book (e.g., bookmark this and send it to Corey). The system can then identify the specific media segment (e.g., a media identifier along with a UTC reference, offset, or the like) and transmit it to the desired contact. In some examples, a user can identify both the starting position and ending position of a desired segment. In other examples, a user can refer to and share particular media stream events (e.g., share this goal with Jordan, send this performance to Susan, etc.). In still other examples, bookmarks and media stream events can be shared through social networks and the like.

As noted above, in response to media-related virtual assistant queries, the system can cue video for playback and/or respond with informational answers (e.g., by displaying a textual response on display 112 or user device 102, speaking a response aloud, or the like). In some examples, the various data feeds and other information used to cue video for playback as discussed herein can be used in a similar manner to determine informational responses to user requests. FIG. 12 illustrates exemplary process 1200 for integrating information into digital assistant knowledge and responding to user requests. At block 1202, a data feed can be received including an event associated with a time in a media stream. The data feed can include any of the data feeds discussed herein with any of the corresponding media stream events 516, such as data feed 510 discussed with reference to FIG. 5, data feed 810 discussed with reference to FIG. 8, and data feed 910 discussed with reference to FIG. 9.

Referring again to process 1200 of FIG. 12, at block 1204, a spoken user request can be received that is associated with the event in the data feed. Users can request information about any media stream event, currently playing media, on-screen player, on-screen actor, or the like. For example, a user can request identification of a scoring player (e.g., “Who scored that goal?”), identification of a penalty call (e.g., “What was that penalty for?”), identification of a performer on screen (e.g., “Who is that?”), identification of a song title (e.g., “What is she singing?”), identification of on-screen show characters (e.g., “What are those characters' names?”), identification of actors in a show (e.g., “Who's in this?”), a description of a plot (e.g., “What's this episode about?”), a description of a series (e.g., “What's this series about?”), or any of a variety of other queries associated with media content.

At block 1206, a response to the user request can be generated based on the data relating to the event (e.g., data from any of the data feeds discussed herein). Any of the media stream events 516 discussed herein can, for example, be searched for informational responses to various queries (e.g., such as the various query examples mentioned above with reference to block 1204). In some examples, responses can be generated based on currently playing media (e.g., a playing show, a paused show, a program shown on screen, etc.). For example, user requests referencing currently playing media can be ambiguous based on speech input alone. Currently playing media can be used to disambiguate user requests and determine user intent by resolving references about current content. For example, a user can request a listing of actors in “this” show (e.g., “Who's in this?”), which can be unclear as the referenced show is not readily apparent from the speech input. The currently playing show, however, can be used to resolve the reference to “this” and identify the user intent. Should the television program example of FIG. 9 be playing, for example, the overview information listed at time 14:00 (UTC) can be used to respond to the user's query by identifying actors Jane Holmes and David Doe.

In other examples, responses can be generated based on a current playback position of currently playing media and/or media content that was previously consumed by the user. For example, a user can request identification of a player who was just shown scoring a goal, and might reference “that” goal in the request (e.g., “Who scored that goal?”). A current playback position of currently playing media can be used to determine user intent and generate a response by resolving “that” goal to the most recent goal that the user was shown whether or not other goals appear later in the media stream. In the example of FIG. 7, current playback position 732 can be used to resolve “that” goal to previous goal 734, and the content of the corresponding media stream event can be used to answer the query. In particular, Player M can be identified as having scored the most recent goal that the user saw. As discussed above with reference to FIG. 7, the current playback position can also be used to determine user intent from various other ambiguous references (e.g., next, previous, etc.), and identified media stream event information can then be used to formulate a response to a query.

In addition, in some examples, a user may want to shift their viewing experience and delay learning of live or updated information. For example, a user may begin watching a sporting event after it has already started or even after it has already finished. Nevertheless, the user may want to experience the entire game as though it were live. In such an instance, available virtual assistant knowledge can be filtered to reference information that was available contemporaneous with a current playback position and avoid reference to information from a point after the current playback position. For example, referring again to the example of FIG. 7, assuming the user is watching at current playback position 732, the system can avoid including next goal 740 in responses. A user can request, for instance, the score at the currently playback position 732 (e.g., “What's the score up to this point?”). In response, the system can provide a score based on previously viewed events (e.g., previous goal 734) while excluding events after current playback position 732 (e.g., next goal 740).

In some examples, a user request can specify that response information should be contemporaneous with a current playback position (e.g., by saying “up to this point,” “until now,” “at this point in the game,” “so far,” etc.) or that response information should be the most updated information available (e.g., by saying “live,” “updated,” “current,” etc.). In other examples, a setting, user preference, or the like can determine whether responses include the most updated information or instead include only information contemporaneous with a playback position. In addition, in some examples, alerts, notifications, messages, social media feed entries, or the like that may be associated with a particular game (e.g., based on terms, names, etc.) can be held back from the user as desired and delivered only after the user arrives at the playback position in the associated content corresponding to the various messages. For example, messages from a friend (e.g., for delivery on user device 102 or any other device) commenting on a live sporting event can be purposely delayed until the user arrives at a point in a delayed viewing of the sporting event corresponding to the time the message was sent, at which point the message can be delivered to the user. In this manner, an entire experience of watching a sporting event (or consuming any other media) can be time-shifted as desired (e.g., to avoid spoiling the results).

In other examples, responses can be generated based on content shown on display 112 by television set-top box 104, content shown on touchscreen 246 of user device 102, and/or metadata associated with any of the displayed content. For example, responses can be generated based on on-screen actors, on-screen players, a list of game participants, a list of actors in a show, a team roster, or the like. As discussed above with reference to FIGS. 6, 11A, and 11B, a variety of information can be derived from displayed content and associated metadata, and that information can be used to disambiguate user requests, determine user intent, and generate responses to user requests. For example, a response to a user request to identify an on-screen player (e.g., “Who is that?”) can be generated based on media stream events near the current playback position, facial recognition, closed captioning text, or the like. In the example of FIG. 6, for instance, media stream events near cued time 624 (e.g., a nearby Team A goal) can be used to identify on-screen player 628 as Player M. In another example, image processing can be used to recognize the jersey number of on-screen player 628 to identify him from a roster as Player M.

Referring again to process 1200 of FIG. 12, at block 1208, the response determined at block 1206 can be caused to be delivered. In some examples, delivering the response can include causing the response to be displayed or played on display 112 via television set-top box 104, on user device 102, or on another device. For example, textual responses and/or media responses can be displayed or played in a virtual assistant interface on a device. In another example, delivering the response can include transmitting the response information to television set-top box 104, user device 102, or another device (e.g., from a server). In still other examples, a user can request identifying information within an image or video (e.g., “Which one is Jennifer?”), and the response can include displaying an indicator (e.g., arrow, dot, outline, etc.) overlaid on the image or video based on coordinates identified, for example, in an associated media stream event. Process 1200 can thus be used to respond to various user queries in a variety of ways by employing timely data incorporated into the virtual assistant knowledge base.

In addition, in any of the various examples discussed herein, various aspects can be personalized for a particular user. User data including contacts, preferences, location, favorite media, and the like can be used to interpret voice commands and facilitate user interaction with the various devices discussed herein. The various processes discussed herein can also be modified in various other ways according to user preferences, contacts, text, usage history, profile data, demographics, or the like. In addition, such preferences and settings can be updated over time based on user interactions (e.g., frequently uttered commands, frequently selected applications, etc.). Gathering and use of user data that is available from various sources can be used to improve the delivery to users of invitational content or any other content that may be of interest to them. The present disclosure contemplates that in some instances, this gathered data can include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, home addresses, or any other identifying information.

The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to deliver targeted content that is of greater interest to the user. Accordingly, use of such personal information data enables calculated control of the delivered content. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure.

The present disclosure further contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data as private and secure. For example, personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection should occur only after receiving the informed consent of the users. Additionally, such entities would take any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices.

Despite the foregoing, the present disclosure also contemplates examples in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of advertisement delivery services, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services. In another example, users can select not to provide location information for targeted content delivery services. In yet another example, users can select not to provide precise location information, but permit the transfer of location zone information.

Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed examples, the present disclosure also contemplates that the various examples can also be implemented without the need for accessing such personal information data. That is, the various examples of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, content can be selected and delivered to users by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the content delivery services, or publicly available information.

In accordance with some examples, FIG. 13 shows a functional block diagram of an electronic device 1300 configured in accordance with the principles of various described examples to, for example, provide voice control of media playback and real-time updating of virtual assistant knowledge. The functional blocks of the device can be implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in FIG. 13 can be combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

As shown in FIG. 13, electronic device 1300 can include a display unit 1302 configured to display media, interfaces, and other content (e.g., display 112, touchscreen 246, or the like). Electronic device 1300 can further include input unit 1304 configured to receive information, such as speech input, tactile input, gesture input, media information, data feeds, media, and the like (e.g., a microphone, a receiver, a touchscreen, a button, a server, or the like). Electronic device 1300 can further include processing unit 1306 coupled to display unit 1302 and input unit 1304. In some examples, processing unit 1306 can include a data feed receiving unit 1308, a user request receiving unit 1310, and a media playback unit 1312.

Processing unit 1306 can be configured to receive (e.g., from input unit 1304 using data feed receiving unit 1308) a data feed, wherein the data feed comprises data relating to an event associated with a time in a media stream. Processing unit 1306 can be further configured to receive (e.g., from input unit 1304 using user request receiving unit 1310) a user request based on speech input, wherein the user request is associated with the event. Processing unit 1306 can be further configured to, in response to receiving the user request, cause (e.g., using media playback unit 1312) playback of the media stream to commence (e.g., on display unit 1302) at the time in the media stream associated with the event.

In some examples, processing unit 1306 can be further configured to interpret the user request based on currently playing media. In other examples, processing unit 1306 can be further configured to interpret the user request based on a current playback position of currently playing media. In still other examples, processing unit 1306 can be further configured to interpret the user request based on one or more of on-screen actors, on-screen players, a list of game participants, a list of actors in a show, a list of characters in a show, or a team roster. In some examples, the media stream comprises a sporting event, and the data relating to the event comprises one or more of a characteristic of a player (e.g., name, nickname, number, position, team, depth chart, experience, style, biographical information, etc.), a score, a penalty, a statistic, or a game segment designator (e.g., quarter, period, half, lap, caution flag, pit stop, down, play, etc.). In other examples, the media stream comprises an awards show, and the data relating to the event comprises one or more of a characteristic of a participant (e.g., name, nickname, character name, biographical information, etc.), a performance description, or an award presentation designator. In still other examples, the media stream comprises a television program, and the data relating to the event comprises one or more of a performance description or a show segment designator.

In one example, the user request (e.g., of user request receiving unit 1310) comprises a request for highlights in the media stream. In some examples, processing unit 1306 can be further configured to, in response to receiving the request, cause consecutive playback of a plurality of segments of the media stream. In other examples, causing playback of the media stream comprises causing media playback on a playback device other than the electronic device. In some examples, the electronic device comprises a server, a set-top box, a remote, a smartphone, or a tablet computer. In other examples, the playback device comprises a set-top box, a smartphone, a tablet computer, or a television. Processing unit 1306 can be further configured to interpret the user request based on information displayed by the electronic device. Processing unit 1306 can be further configured to interpret the user request based on information displayed by the playback device.

In some examples, the data relating to the event comprises closed captioning text. Processing unit 1306 can be further configured to determine the time in the media stream associated with the event based on the closed captioning text. In one example, the data relating to the event comprises one or more of secondary screen experience data, secondary camera view data, or social network feed data. Processing unit 1306 can be further configured to receive a bookmark indication from the user, wherein the bookmark corresponds to a particular playback position in the media stream. Processing unit 1306 can be further configured to receive a user request to share the bookmark, and, in response to receiving the user request to share the bookmark, cause cue information associated with the particular playback position to be transmitted to a server. Processing unit 1306 can be further configured to interpret the user request based on one or more of a user's favorite team, a user's favorite sport, a user's favorite player, a user's favorite actor, a user's favorite television show, a user's geographical location, a user demographic, a user's viewing history, or a user's subscription data.

In accordance with some examples, FIG. 14 shows a functional block diagram of an electronic device 1300 configured in accordance with the principles of various described examples to, for example, integrate information into digital assistant knowledge and respond to user requests. The functional blocks of the device can be implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in FIG. 14 can be combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

As shown in FIG. 14, electronic device 1400 can include a display unit 1402 configured to display media, interfaces, and other content (e.g., display 112, touchscreen 246, or the like). Electronic device 1400 can further include input unit 1404 configured to receive information, such as speech input, tactile input, gesture input, media information, data feeds, media, and the like (e.g., a microphone, a receiver, a touchscreen, a button, a server, or the like). Electronic device 1400 can further include processing unit 1406 coupled to display unit 1402 and input unit 1404. In some examples, processing unit 1306 can include a data feed receiving unit 1408, a user request receiving unit 1410, a response generating unit 1412, and a response delivering unit 1414.

Processing unit 1406 can be configured to receive (e.g., from input unit 1404 using data feed receiving unit 1408), a data feed, wherein the data feed comprises data relating to an event associated with a time in a media stream. Processing unit 1406 can be further configured to receive (e.g., from input unit 1404 using user request receiving unit 1410) a user request based on speech input from a user, wherein the user request is associated with the event. Processing unit 1406 can be further configured to generate (e.g., using response generating unit 1412) a response to the user request based on the data relating to the event. Processing unit 1408 can be further configured to cause (e.g., using response delivering unit 1414) the response to be delivered.

In some examples, generating the response (e.g., using response generating unit 1412) further comprises generating the response based on currently playing media. In other examples, generating the response (e.g., using response generating unit 1412) further comprises generating the response based on a current playback position of currently playing media. In still other examples, generating the response (e.g., using response generating unit 1412) further comprises generating the response based on media content previously consumed by the user. In some examples, generating the response (e.g., using response generating unit 1412) further comprises generating the response based on one or more of on-screen actors, on-screen players, a list of game participants, a list of actors in a show, or a team roster.

In some examples, processing unit 1406 can be further configured to, in response to the user request comprising a request for information contemporaneous with a current playback position of currently playing media, generate the response based on data contemporaneous with the current playback position, wherein the data contemporaneous with the current playback position excludes data associated with a time after the current playback position; and, in response to the user request comprising a request for live information, generate the response based on live data. In some examples, causing the response to be delivered (e.g., using response delivering unit 1414) comprises causing the response to be displayed or played on a playback device other than the electronic device. In other examples, causing the response to be delivered (e.g., using response delivering unit 1414) comprises causing the response to be delivered to a playback device other than the electronic device. In some examples, the electronic device comprises a server, a set-top box, a remote, a smartphone, or a tablet computer. In other examples, the playback device comprises a set-top box, a smartphone, a tablet computer, or a television. In some examples, processing unit 1406 can be further configured to interpret the user request based on information displayed by the electronic device. In other examples, processing unit 1406 can be further configured to interpret the user request based on information displayed by the playback device.

Although examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art (e.g., modifying any of the systems or processes discussed herein according to the concepts described in relation to any other system or process discussed herein). Such changes and modifications are to be understood as being included within the scope of the various examples as defined by the appended claims. 

What is claimed is:
 1. A method for integrating information into digital assistant knowledge, the method comprising: at an electronic device: receiving a data feed, wherein the data feed comprises data relating to an event associated with a time in a media stream; receiving a user request based on speech input from a user, wherein the user request is associated with the event; determining, based on the user request, a user intent; generating a response to the user request based on the data relating to the event, the user intent, a current playback position of currently playing media, and a predefined user preference, wherein the predefined user preference enables a determination of whether to include, within the generated response, up-to-date information regardless of the current playback position; and causing the response to be delivered.
 2. The method of claim 1, wherein generating the response further comprises generating the response based on currently playing media.
 3. The method of claim 1, wherein generating the response further comprises generating the response based on media content previously consumed by the user.
 4. The method of claim 1, wherein generating the response further comprises generating the response based on one or more of on-screen actors, on-screen players, a list of game participants, a list of actors in a show, or a team roster.
 5. The method of claim 1, further comprising: in response to the user request comprising a request for information contemporaneous with a current playback position of currently playing media, generating the response based on data contemporaneous with the current playback position, wherein the data contemporaneous with the current playback position excludes up-to-date data associated with a time after the current playback position; and in response to the user request comprising a request for up-to-date information, generating the response based on up-to-date data.
 6. The method of claim 1, wherein causing the response to be delivered comprises causing the response to be displayed or played on a playback device other than the electronic device.
 7. The method of claim 1, wherein causing the response to be delivered comprises causing the response to be delivered to a playback device other than the electronic device.
 8. The method of claim 1, wherein determining the user intent further comprises determining the user intent based on one or more additional predefined user preferences, wherein the one or more additional predefined user preferences are previously defined by a user.
 9. The method of claim 1, wherein determining the user intent further comprises determining the user intent based on one or more additional predefined user preferences, wherein the one or more additional predefined user preferences are associated with the media stream.
 10. The method of claim 1, wherein the response is delivered without interrupting playback of the currently playing media.
 11. The method of claim 1, wherein causing the response to be delivered does not interrupt the current playback position.
 12. A non-transitory computer-readable storage medium comprising computer-executable instructions for: receiving a data feed, wherein the data feed comprises data relating to an event associated with a time in a media stream; receiving a user request based on speech input from a user, wherein the user request is associated with the event; determining, based on the user request, a user intent; generating a response to the user request based on the data relating to the event, the user intent, a current playback position of currently playing media, and a predefined user preference, wherein the predefined user preference enables a determination of whether to include, within the generated response, up-to-date information regardless of the current playback position; and causing the response to be delivered.
 13. The non-transitory computer-readable storage medium of claim 12, wherein generating the response further comprises generating the response based on currently playing media.
 14. The non-transitory computer-readable storage medium of claim 12, wherein generating the response further comprises generating the response based on media content previously consumed by the user.
 15. The non-transitory computer-readable storage medium of claim 12, wherein causing the response to be delivered comprises causing the response to be displayed or played on a playback device other than the electronic device.
 16. The non-transitory computer-readable storage medium of claim 12, further comprising instructions for: in response to the user request comprising a request for information contemporaneous with a current playback position of currently playing media, generating the response based on data contemporaneous with the current playback position, wherein the data contemporaneous with the current playback position excludes up-to-date data associated with a time after the current playback position; and in response to the user request comprising a request for up-to-date information, generating the response based on up-to-date data.
 17. The non-transitory computer-readable storage medium of claim 12, wherein causing the response to be delivered does not interrupt the current playback position.
 18. A system for integrating information into digital assistant knowledge, the system comprising: one or more processors; memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: receiving a data feed, wherein the data feed comprises data relating to an event associated with a time in a media stream; receiving a user request based on speech input from a user, wherein the user request is associated with the event; determining, based on the user request, a user intent; generating a response to the user request based on the data relating to the event, the user intent, a current playback position of currently playing media, and a predefined user preference, wherein the predefined user preference enables a determination of whether to include, within the generated response, up-to-date information regardless of the current playback position; and causing the response to be delivered.
 19. The system of claim 18, wherein generating the response further comprises generating the response based on currently playing media.
 20. The system of claim 18, wherein generating the response further comprises generating the response based on media content previously consumed by the user.
 21. The system of claim 18, wherein causing the response to be delivered comprises causing the response to be displayed or played on a playback device other than the electronic device.
 22. The system of claim 18, wherein causing the response to be delivered does not interrupt the current playback position. 